Thank you!

I'm not sure we want to show writing this much to nvs - see the warning here: https://doc.atomvm.org/latest/programmers-guide.html#non-volatile-storage

Maybe change it to RTC https://doc.atomvm.org/latest/programmers-guide.html#rtc-memory - which obviously doesn't survive power outs, but doesn't wear down the flash..

Oh that makes sense — frequent writes to NVS are a bad pattern. I can convert the counter to RTC and revise the NVS usage to something that doesn’t write often, resulting in two examples.

yeah, remember to try/catch the rtc_slow_get_binary() - as it will raise badarg when not set eg for you on first boot..

Thanks for the feedback.

I updated the examples to avoid frequent NVS writes:

• EspNvs now writes the default value only once (when the key is missing) and then just logs the fetch result before restarting.
• The restart counter example was moved to EspRtc using RTC slow memory (so it survives software resets without wearing flash).

Example output:

EspNvs:

Fetched word from NVS: AtomVM
Restarting in 10 seconds ...

EspRtc:

Loading count from RTC slow memory ...
This device has restarted 2 time(s).
Saving count to RTC slow memory ...
Restarting in 10 seconds ...

I'm not sure we want to show writing this much to nvs - see the warning here: https:

Excellent point! I should have caught this.

We could also add standardized .gitignore and .formatter.exs files across all Elixir examples for consistency.

Potentially .tool-versions as well.

I'm wondering what the ideal name for the RTC slow memory example would be. Should we use something more specific, like EspRtcSlowMemory?

I'm wondering what the ideal name for the RTC slow memory example would be. Should we use something more specific, like EspRtcSlowMemory?

I think EspRtcMemory is good.

We could also add standardized .gitignore and .formatter.exs files across all Elixir examples for consistency.

Potentially .tool-versions as well.

I would not add .tool-versions, this should be up to the users choice.

.gitignore is fine, but for simplicity I would prefer just one set of rules in the root directory, it can get harder to keep track of individual files through the directory tree.

I am not sure if we need a formatter.exs, we just want to follow default formatting rules. But I am much more familiar with Erlang and erlfmt, which is what we use for all AtomVM org repos.

Agree, I suggest not handling the projectwide .gitignore here though - also something good about seeing the avm file in git diff etc. so maybe no .gitignore is needed..

this is great!

I will have to admit I'm backtracking on the %__MODULE__{} once I see it - while it's obvious to us, for a beginner it looks very advanced and implicit..

Should we have RebootState.ex in a separate file? then we also show good separation of everything.. and it's obvious to a beginner..

Sorry about not thinking the feedback through!